I ran across this and thought I would post it up to see if it were me or the new software.
Attachment 66358
Printable View
I ran across this and thought I would post it up to see if it were me or the new software.
Attachment 66358
What browser are you using?? I am using Firefox 4 and have not had any issues but I tested it with IE and Safari and was getting some funky things like that with IE ( I think I have 8 but can't remember since I don't use it that often anymore ).
A few people had reported that but the screen capture is helpful.
The next time that happens can you view the page source and send it to me in a PM? That would be helpful as well.
Knowing which browser and version would be helpful as well.
Thanks!
I am using Internet Exporer version 8.0.6001 and have all kinds of problems now with this. What you see above from the OP is teh same screen capture I wold post in here. There is a scroll bar at the bottom of the page. It used to not have that and you could see the whole page. Now, the posters info bleeds into the main text area of the post. Of the 4 razor forums I have, Badger & Blade, Shve Den, Shave Ready, and Straightrazor Place, this is the only one with the issues. It "used" to work fine. Now it doesn't work fine. You almost need to mirror the forum on a different part of the server to test out the compatibilty issues with all the browsers. Fire Fox may work but not everyone uses Fire Fox, nor Apple products.
Firefox/Mozilla is not an apple product. Those of us fortunate enough to have abandoned Microsoft and windows for Linux free ware are not having to contend with the glitches shown. You can still run Firefox on a windows box. You might give it a try until the devs get the glitches worked out on the systems you're running.
Thanks for the suggestion. Please let me know where should I send you the bill for the hours I've spent doing exactly this?
Eric has been spending a lot of time fixing things like this, but unless you guys start reading his posts more carefully, and do your part, I'm afraid you'll either have to live with the current state, or find your answers on one of the many other shaving forums.
Here is how post number three in this thread looks like no matter which browser I use (I don't use windows):
Attachment 66550
FYI... From the one person that did send me a PM about this (HUGE THANKS to that person, btw...), I got:
If someone can send me something to work with I can start troubleshooting it.Quote:
I only saw the problem once. If it duplicates someplace, I'll be sure to let you know. I would not spend too much time on it if you cannot duplicate it.
In the meantime I don't know where to write the hacks to make your browser accept W3C compliant CSS.
I just did some testing here at work ( slow day so far) and found that I get the same error if I have Compatibility Mode set under the Tools menu in IE. Once I turn it off everything looks good so you may want to check that out Gibbs. Also Firefox and Safari as well as Opera are all browsers you can get for Windows. I have to use all 4 as my job requires it for troubleshooting web based apps.
HNSB if you still want it I can send you a copy of the Source I am looking at but seems to be specific to IE and Compatibility Mode only.
I've not had problems, but for some reason my setup (T42 laptop/openSuse 11.x/Firefox3.6) displays text and background as almost the exact same shade in the classifieds, and I'm having a really hard time reading. I've noted that on my desktop, running windoze and Firefox 3.6 shows the background as white and the text as dark gray, but it sure looks like light gray background on my laptop.
Alright, I'm probably going to sound like a jerk, but I can't help ranting when I feel somebody keeps wasting my time.
Here's my vanilla installation of Windows 7 Professional, right out the box.
Attachment 66597
Attachment 66600
Works perfectly, huh?
And here is how it looks after checking off the 'Compatibility Mode'.
Attachment 66599
So my question is why would you use compatibility mode? The tooltip from Microsoft says that it would improve websites designed for old browsers.
Attachment 66598
Honestly, I don't care if you chose to view a modern website with a 10 year old technology. Regressing a modern browser to behave as something ancient is your choice and I don't have the time, or the desire to deal with such nonsense unless you are willing to compensate me appropriately (the balpark is dozens of custom razors).
And, yes I can very easily disable the 'Thanks', put a limit on how many letters can be used for 'location', or disable it altogether, or use different layout where the avatar is positioned in it's separate band above the post body, which would make you scroll 40% more...
Tried your suggestion, Toggie. Works. I unchecked the box that says use compatibility view on all web sites. Refreshed the page and the type is back in the proper spaces. There is a name for those boxes, I believe called "Frames". W3C is different depending on whether you use "strict" or "transitional" for the passing of their test.
Here is the W3C link for validator page: http://validator.w3.org/ put the address of this page in the required box and click validate and you get 2 errors for XHTML Tansitional Maybe that source info will be useful.
However, the real problem might be found in your CSS (Cascadeing Style Sheets) coding. This link: http://jigsaw.w3.org/css-validator/ will let you run the CSS validation of a page, and on this particular page it has 387 errors for CSS.
Just an addition. Important enough I thought to add a new reply. At work now, and on IE8 there is an icon represting broken page (upper part of your IE8 browser, next to the address bar, in fact RIGHT next to it, click it. One way it works, other way it's a bit garbled.
NOTE: the page will refresh automatically if you click on that broken page icon.
Thanks to whoever figured out compatibility mode. This problem makes sense now. I don't think Im going to spend time on it in the near future as it's isolated to one setting on one browser. There are other more important things to spend time on right now.
The problem is not with the CSS. Most of those CSS errors are irrelevant - though there are two or three minor things that should be fixed.
Oh, and SRP doesn't use frames.